home *** CD-ROM | disk | FTP | other *** search
/ SGI Performance Co-Pilot 1.3 / SGI Performance Co-Pilot 1.3.iso / dist / dist6.4 / pcp.idb / usr / share / catman / u_man / cat3 / PMAPI / pmdestroycontext.z / pmdestroycontext
Text File  |  1997-04-03  |  4KB  |  67 lines
  1.  
  2.  
  3.  
  4. PPPPMMMMDDDDEEEESSSSTTTTRRRROOOOYYYYCCCCOOOONNNNTTTTEEEEXXXXTTTT((((3333))))                                        PPPPMMMMDDDDEEEESSSSTTTTRRRROOOOYYYYCCCCOOOONNNNTTTTEEEEXXXXTTTT((((3333))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      ppppmmmmDDDDeeeessssttttrrrrooooyyyyCCCCoooonnnntttteeeexxxxtttt - destroy a PMAPI context
  10.  
  11. CCCC SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  12.      ####iiiinnnncccclllluuuuddddeeee <<<<ppppccccpppp////ppppmmmmaaaappppiiii....hhhh>>>>
  13.  
  14.      iiiinnnntttt ppppmmmmDDDDeeeessssttttrrrrooooyyyyCCCCoooonnnntttteeeexxxxtttt((((iiiinnnntttt hhhhaaaannnnddddlllleeee))))
  15.  
  16.      cccccccc ............ ----llllppppccccpppp
  17.  
  18. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  19.      An application using the Performance Metrics Application Programming
  20.      Interface (PMAPI) may manipulate several concurrent contexts, each
  21.      associated with a source of performance metrics, e.g. ppppmmmmccccdddd(1) on some
  22.      host, or an archive log of performance metrics as created by ppppmmmmllllooooggggggggeeeerrrr(1).
  23.  
  24.      ppppmmmmDDDDeeeessssttttrrrrooooyyyyCCCCoooonnnntttteeeexxxxtttt destroys the PMAPI context identified by _h_a_n_d_l_e.
  25.      Typically this would imply some termination of a connection to a PMCD or
  26.      closing an archive log file, and orderly clean-up.
  27.  
  28.      The context must have been previously created using ppppmmmmNNNNeeeewwwwCCCCoooonnnntttteeeexxxxtttt(3) or
  29.      ppppmmmmDDDDuuuuppppCCCCoooonnnntttteeeexxxxtttt(3).
  30.  
  31.      On success, ppppmmmmDDDDeeeessssttttrrrrooooyyyyCCCCoooonnnntttteeeexxxxtttt returns zero.  If _h_a_n_d_l_e was the current
  32.      PMAPI context, then the current context becomes undefined.  This means
  33.      the application must explicitly re-establish a valid PMAPI context with
  34.      ppppmmmmUUUUsssseeeeCCCCoooonnnntttteeeexxxxtttt(3), or create a new context with ppppmmmmNNNNeeeewwwwCCCCoooonnnntttteeeexxxxtttt(3) or
  35.      ppppmmmmDDDDuuuuppppCCCCoooonnnntttteeeexxxxtttt(3), before the next PMAPI operation that requires a PMAPI
  36.      context.
  37.  
  38. SSSSEEEEEEEE AAAALLLLSSSSOOOO
  39.      PPPPMMMMAAAAPPPPIIII(3), ppppmmmmDDDDuuuuppppCCCCoooonnnntttteeeexxxxtttt(3), ppppmmmmNNNNeeeewwwwCCCCoooonnnntttteeeexxxxtttt(3), ppppmmmmUUUUsssseeeeCCCCoooonnnntttteeeexxxxtttt(3) and
  40.      ppppmmmmWWWWhhhhiiiicccchhhhCCCCoooonnnntttteeeexxxxtttt(3).
  41.  
  42. DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
  43.      PPPPMMMM____EEEERRRRRRRR____NNNNOOOOCCCCOOOONNNNTTTTEEEEXXXXTTTT
  44.  
  45.           _h_a_n_d_l_e does not identify a valid PMAPI context
  46.  
  47.  
  48.  
  49.  
  50.  
  51.  
  52.  
  53.  
  54.  
  55.  
  56.  
  57.  
  58.  
  59.  
  60.  
  61.  
  62.  
  63.                                                                         PPPPaaaaggggeeee 1111
  64.  
  65.  
  66.  
  67.